home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d1
/
ems_util.arc
/
EMS-UTIL.DOC
< prev
next >
Wrap
Text File
|
1989-10-26
|
5KB
|
89 lines
EMS Utilities
Since its intoduction a few years ago at Comdex, the Lotus/Intel/Microsoft
(LIM) Expanded Memory Specification (EMS) has gained wide popularity. Since
it can be retrofitted onto virtually any IBM-PC type machine (even 8088-based
systems), it provides a unified method for implementing memory outside the
640K limit imposed by MS-DOS. As such, several major packages now support EMS
memory, when available, and their numbers are constantly growing. It thus
makes sense to add EMS-type memory when upgrading a system.
The availability of EMS memory is indeed useful when applications are run
that can use it, but what about the rest of the time? DOS certainly doesn't
use EMS memory (at least, not directly), nor do the vast majority of the
"small" programs that are typically run when major applications are not. Is
all this expensive RAM simply to go to waste during these times, simply for
the sake of a few programs that do use EMS?
The answer is no. In this ZIP file are three (actually, four) utilities that
can make good use of EMS memory when it is not being used by an application.
Three very useful services are provided: a RAM disk, a hard disk cache, and a
print spooler. All of them (except for one of the RAM disk programs) can be
disabled and re-enabled by command-line instructions, rather than by
re-booting the computer. As such, they provide good "idle" tasks for EMS
memory during periods when it would otherwise go to waste. When an EMS-using
application needs EMS memory, the utilties can be disabled (typically with a
batch file that also invokes the application), and then re-enabled when the
application exits.
The author has investigated nearly all of the PD and shareware programs
available from BBS'es and other sources, and has selected these as
best-of-class. All of them, except the Nifty-James RAM disk, are currently in
use on the computer I am writing this DOC file with. They have been pretty
well tested and have been found to work reliably with CodeView (a major
accomplishment by itself) and Turbo Debugger, as well as with QEMM and
Nu-Mega 386 EMS drivers. All of them can be high-loaded. They should also
work with 386-to-the-MAX and CEMM.
DMP200 is the print spooler. It is the best I've seen. It is particularily
nice since it only allocates EMS memory when it needs it, and immediately
frees it when it is done with it. As such, you don't need to disable it in
any way when running an EMS-utilizing application. It also provides many
other services; read the DOC manual that comes with it.
EMC110 is a great hard disk cache program. It is the only one I've seen that
both uses EMS memory and allows dynamic resizing of the buffer. It does have
some compatibility constraints; so read the DOC file. I can tell you that it
does work with all Western Digital controllers (if no hard disk partitioning
utility is used) and with the Future Domain TMC-881 SCSI controller (which is
what I use). Futhermore, Golden Bow's VFeature is compatible, but On-Track
System's Disk Manager is not. As for other hard disk partitioning utilties,
you will probably need to call the manufacturer; in particular, I do not know
if SpeedStor will work with it. When calling the manufacturer, read the
representive the fisrt paragraph or so of the "Technical Notes" section. When
designing a batch file for running the EMS application, use the following
template:
emc110 x
application %1 %2 %3 %4 %5 %6 %7 %8 %9
emc110
This disables the cache (freeing up the EMS memory it was using) for the
duration of the application, and then re-instates it when the application
exits.
Two RAM disks are provided in the package, which address different needs.
NJRAMD12 (Nifty-James) is fast and uses very little conventional memory, but
the amount of EMS memory it uses can be modified only by editing the
CONFIG.SYS file and rebooting. ADJRAM41, on the other hand can have its usage
of EMS memory altered (all the way to zero), but uses at least 15K of
conventional memory (which can be high-loaded on 386 machines, however). Most
users would never want to change the dimensions of their RAM disk, so
Nifty-James is appropriate. For the unusual users (like me), who need to
sometimes free up ALL of the EMS memory, ADJRAM41 is called for.
A word of caution if using ADJRAM41: despite what the documentation says, the
intial size of the RAM disk should be set to 15K, not 32K, unless you are
comtemplating an unusual configuration for your system. The idea is to use as
little conventional memory as possible. *** READ THE DOCUMENTATION BEFORE
USING ADJRAM41 !!! ***
I hope you find these utilities as useful as I have.
Randy Langer
MicroSphere Technology, Inc.
PO Box 620
Magalia, CA 95954